5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
- Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-1: ILF Integration

The Compilation Step


When you define an ILF routine, it becomes an integral part of the associated APPX process. To achieve this integration, the ILF routines are compiled along with all the other process specifications that you entered. The APPX process compiler is invoked automatically at process runtime. The compiler pulls together all the parts of the application, including any ILF routines that you defined. As a designer, you do not have to be concerned about the compilation step other than to understand that, if any errors are encountered, you will receive an appropriate compilation error message (refer to the next section).

The system automatically invokes compilation at runtime when it is required, either when a process is first developed or if changes were made. The system checks to see if there were any changes since the last compilation and, if there were, a recompilation is automatically initiated. Note that the verification and compilation is done when an end user executes a process, not when the designer applies changes or makes additions to the process specifications. As a result, the start-up time for an end user is longer when a compilation is required. Once compiled, subsequent start-up time is much faster because the system uses the compiled version (called an executable module or EM).

You may also force a process to compile while using Application Design. Simply position your cursor on the selected process and select syntax check from the Toolbox menu (or simply select Option 97).

Application Design Manual                                         "Powered by Appx Software"

514

©2006 By APPX Software, Inc. All Rights Reserved